fix(drift): retry transient OpenAPI spec fetch failures#161
Merged
Conversation
A 502 Bad Gateway from the spec endpoint was aborting the scheduled drift-detection workflow and triggering noisy Slack alerts. Wrap the spec fetch in an exponential-backoff retry (4 attempts, jittered, per-attempt 30s timeout) that retries on 5xx/429 and network errors while still failing fast on 4xx.
063b8a6 to
d2bc9aa
Compare
nastassiafulconis
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
502 Bad Gatewayresponses fromapi.agentic.scope3.com/api/v2/buyer/openapi.yaml, since the script currently does a single unretriedfetch.fetchWithRetryhelper (4 attempts, exponential backoff with jitter, 30s per-attempt timeout) that retries on 5xx/429 and network errors, and routefetchSpecEndpointsthrough it so non-transient 4xx still fail fast.as Record<string, any>cast on the parsed spec to a narrower typed shape so the file passes the repo'sno-explicit-anyrule.Test plan
npm run type-check— cleannpm run detect-drift -- --json— happy path still produces the expected JSON reporthttps://httpbin.org/status/502— 3 retry attempts logged to stderr with increasing delays, then a clear "Failed to fetch … after 4 attempts" errorhttps://httpbin.org/status/404— returns immediately with no retriesAPI Drift Detectionworkflow viaworkflow_dispatchto confirm a normal run still completes cleanly